-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
202 fix trimming@main #203
Conversation
Code Coverage Summary
Diff against main
Results for commit: 61b1e36 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am looking into it and as I thought we need basically to rewrite wrap_txt and wrap_string. They do a poor job at keeping the original string intact and it is not well documented (in-code helper functions e.g.). I was thinking that this could have been avoided for longer as it is not extremely necessary to allow users to add spaces and newlines everywhere, but we need the flag to be able to do so eventually, also considering the case of decimal alignment. If anything, these functions do not have any test nor example and we need to compartmentalize the issue and the solution bottom-up
Looks great! It seems to cause failures for listings because of the unused arguments in |
I have a couple of tests failing in rtables with the change (exporters and pagination). |
Co-authored-by: Emily de la Rua <59304861+edelarua@users.noreply.github.com> Signed-off-by: Davide Garolini <dgarolini@gmail.com>
Indeed something changed because the split of words is not optimal as it was before. Before:
Now:
I will try to make it a bit smarter by taking into account the word before, but there is not a simple solution to this I think |
…g/formatters into 202_fix_trimming@main
btw for the reviewers @edelarua @ayogasekaram: 250+ line additions are simply comments, missing documentation, and missing tests. There were NO direct tests of the wrapping, hence imo the source of multiple problems and bugs downstream. Nonetheless, the wrapping algorithm now is entirely new and it has nothing shared with the old method. I kept
|
Signed-off-by: Davide Garolini <dgarolini@gmail.com>
…g/formatters into 202_fix_trimming@main
This is good to go! :) |
See insightsengineering/formatters#203 --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
closes #202
related to rtables issue #630